-
Notifications
You must be signed in to change notification settings - Fork 121
Integrate periphery: add fancier reporting #15984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
|
CI build with no violation looks like this 🎉 |
Add --disable-update-check and --relative-results flags DRY some code to avoid repetition of the commands to run scan
a257cc4 to
0203b2f
Compare
|
CI build with some violations (added on purpose here) looks like this: (Note that the violations are still printed in the CI job logs too; so if someone doesn't know to look at the annotations and for some reason just looked at the job logs instead they'd still see the same info) |
This reverts commit 0203b2f.
|
@RafaelKayumov Dummy changes I made to introduce fake violations have been reverted and both cases have been tested, so the PR is now ready for review 😃 (I should have set the PR to draft while I was experimenting… sorry… 🙃 ) |



Note
This PR targets the HEAD branch
integrate-peripheryof #15962This PR adds some optional improvements/suggestions on top of #15962.
Feel free to discard, or keep, or only merge later, but I figured opening a separate PR would allow to unblock the merging of the main one while allowing to iterate on improvements if needed 🙂
.buildkite/commands/run-periphery.shsetup-and-run-periphery.shperiphery scan "$@"--disable-update-checkflag in the periphery call since thesetup-and-run-periphery.shscript already handles version checks--relative-resultsflag to use relative paths in the output (instead of the absolute paths which are long and not super useful especially in CI context)